Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

Notes/Domino 6 and 7 Forum

Notes/Domino 6 and 7 Forum


  

PreviousPrevious NextNext

Sure...
~Umberto Nongeroson 15.Nov.03 04:36 AM a Web browser
Domino Designer 6.0.1 CF2 iSeries


I'm not sure of your knowledge level so I'll start at the basics...
  1. If you view source for any frameset you'll see it's very simple...typically less than 10 lines. (note: not view source for a frame inside the frameset...that'll be complex...but just the frameset itself...typically view source from a menu in IE and not right-clicking).
  2. If you copy the source from an existing frameset you can paste it into a form. Set the form's content type as HTML. and then you can view the form by previewing it, but use ?ReadForm instead of ?OpenForm.
  3. Now that you're convinced that you can serve up an exact copy of your original frameset from a form instead of just a frameset design, have a look at the frameset code in the form you designed. You'll notice that the default content for each frame is specified in the frameset html.
  4. Since you're now serving up the frameset from a form, you should know that you can pass any set of values to a form through appending "&keyA=blahblah&keyB=xyzabc" and the like. These values can be accessed in the form design through Query_String...and you can read up about it in the Designer Help. Also, take a look at @WebDbName and @URLQueryString (R6 features by the way, but any version of Domino can get at the Query_String and simulate @WebDbName through longer methods...the R4/5 forum should have lots of answers there).
  5. It's pretty simple to change the hard-coded frame source references to a "Computed Text" element that uses @WebDbName and @URLQueryString to display whatever default content you want for each frame.
  6. For example, if you always want a top navigation frame that is static you'd have that frame src always compute to "/" + @WebDbName + "the rest of the url". However, if the content frame is variable the src reference would be along the lines of "/" + @WebDbName + "/maybeotherstuff" + @UrlQueryString("contentId") + "the rest of the url". You'll have to assemble your own URLs and I can't give you much more advice here without knowing more. The URL that would launch your frameset with custom content would be along the lines of "http://www.acme.com/path/database.nsf/framesetForm?ReadForm&contentId=whateveryouwant". You'd use "/" + @WebDbName to get the first part dynamic and then you can set the rest up however you want. I typically pass a doc UNID and then assemble my frame source to go to the document through a view sorted by UNID. You can pass multiple variables/values if you need to.

I hope this helps. It's a very powerful tool once you get the hang of it.

...Neil




Open a Specific Document in Framese... (~Naomi Ekponepl... 13.Nov.03)
. . RE: Open a Specific Document in Fra... (~Evelyn Breboos... 13.Nov.03)
. . . . RE: Open a Specific Document in Fra... (~Naomi Ekponepl... 13.Nov.03)
. . Sure... (~Paul Opfanakon... 15.Nov.03)


Document Options






  Document options
Print this pagePrint this page

Search this forum

Forum views and search


  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Category
Platform
Release
Advanced search

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS